Multi-connection access point

ABSTRACT

Example implementations relate to multi-connection access points. For example, an access point can include instructions to: establish a first connection to a first controller, wherein the access point receives configuration data from the first controller to generate a first virtual access point with the first controller; and establish a second connection to a second controller, wherein the access point receives configuration data from the second controller to generate a second virtual access point with the second controller.

BACKGROUND

Networks can include a plurality of access points that are controlled bya controller. The controller can be a centralized controller for theplurality of access points. The controller can be utilized to manage,configure, monitor, and/or troubleshoot the plurality of access pointswithin a network. The controller can be utilized to encrypt and/ordecrypt data packets received from the plurality of access points. Thecontroller can be utilized to configure the plurality of access pointsand/or change a configuration of the plurality of access points.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example environment for multi-connection accesspoint, consistent with the present disclosure.

FIG. 2 further illustrates an example method for multi-connection accesspoint, consistent with the present disclosure.

FIG. 3 illustrates an example architecture for multi-connection accesspoint, consistent with the present disclosure.

FIG. 4 is a block diagram of an example system for multi-connectionaccess point, consistent with the present disclosure.

FIG. 5 is a block diagram of an example method for multi-connectionaccess point, consistent with the present disclosure.

DETAILED DESCRIPTION

Multi-connection access point systems can enable a plurality ofdifferent controllers to control functions of a single access pointwithin a network. As used herein, a controller (e.g., networkcontroller) can be a network device that can be utilized to manage,configure, monitor, and/or troubleshoot access points within a network(e.g., wireless network, local area network (LAN), wide area network(WAN), Internet, etc.). As used herein, ‘access point’ (AP) generallyrefers to receiving points for any known or convenient wireless accesstechnology which may later become known. Specifically, the term AP isnot intended to be limited to IEEE 802.11-based APs. APs generallyfunction as an electronic device that is adapted to allow wirelessdevices to connect to a wired network via various communicationsstandards. The network can include a plurality of access points toenable computing devices to exchange data. In some examples, a firstcomputing device can exchange data packets with a second computingdevice via a plurality of access points.

The multi-connection access point systems can utilize a plurality ofcontrollers to manage access points of the network. In some examples,the plurality of controllers can manage the same access points of thenetwork. For example, the plurality of access points can include aplurality of ESSIDs that correspond to the plurality of controllers. Inthis example, an access point from the plurality of access points candirect data packets to a particular controller of the plurality ofcontrollers based on an ESSID of the data packets received by theplurality of access points. For example, a first controller can have afirst ESSID and a second controller can have a second ESSID. In thisexample, an access point can include the first ESSID and the secondESSID. In this example, the access point can direct data packets withthe first ESSID to the first controller and direct packets with thesecond ESSID to the second controller. In some examples, the firstcontroller and the second controller can be separated by an air gap. Asused herein, an air gap is a network security measure to physicallyisolate a first network from a second network such that communicationdoes not exist between the first network and the second network.

The multi-connection access point system can enable a plurality ofaccess points to be managed by a plurality of different controllerssimultaneously. In some examples, the multi-connection access pointsystem can be utilized separate a first type of data to a firstcontroller and a second type of data to a second controller based on anESSID of the data. In some examples, the first controller can beutilized by a first entity and the second controller can be utilized bya second entity. In these examples, the first controller and the secondcontroller can be separated by an air gap to secure data of the firstentity from the second entity and vice versa. In other examples, thefirst controller can be utilized to encrypt or decrypt data packets witha first security level and the second controller can be utilized toencrypt or decrypt data packets with a second security level.

FIG. 1 illustrates an example environment 100 for multi-connectionaccess point, consistent with the present disclosure. The environment100 can represent a network with a plurality of access points 102-1,102-2, 102-3 in communication with a plurality of controllers 106-1,106-2, 106-3. In some examples, the plurality of access points 102-1,102-2, 102-3 can be coupled to a number of devices (e.g., user devices,mobile devices, etc.) to transmit data packets from the number ofdevices to one or more of the plurality of controllers 106-1, 106-2,106-3.

In some examples, each of the plurality of access points 102-1, 102-2,102-3 can be coupled to each of the plurality of controllers 106-1,106-2, 106-3. In these examples, the plurality of access points 102-1,102-2, 102-3 can include a corresponding ESSID to each of the pluralityof controllers 106-1, 106-2, 106-3. For example, the access point 102-1can be coupled and/or managed by controller 106-1 via pathway 112-1 witha corresponding ESSID. In this example, the access point 102-1 can alsobe coupled and/or managed by controller 106-2 via pathway 112-2 with acorresponding second ESSID. In this example, the access point 102-1 canalso be coupled and/or managed by controller 106-3 via pathway 112-3with a corresponding third ESSID.

Each of the plurality of controllers 106-1, 106-2, 106-3 can be within acorresponding zone of a plurality of zones 104-1, 104-2, 104-3. In someexamples, each of the plurality of zones 104-1, 104-2, 104-3 can beseparated by air gaps 108-1, 108-2. For example, zone 104-1 and zone104-2 can be separated by air gap 108-1. Separating each of theplurality of zones 104-1, 104-2, 104-3 by air gaps 108-1, 108-2 canprevent communication between each of the plurality of controllers106-1, 106-2, 106-3. In addition, separating each of the plurality ofzones 104-1, 104-2, 104-3 by air gaps 108-1, 108-2 can allow a firstcontroller of the plurality controllers 106-1, 106-2, 106-3 to managethe plurality of access points 102-1, 102-2, 102-3 without affecting asecond controller of the plurality of controllers 106-1, 106-2, 106-3from separately managing the plurality of access points 102-1, 102-2,102-3.

In some examples, each of the plurality of controllers 106-1, 106-2,106-3 can utilize a particular communication protocol. For example, thecontroller 106-1 can utilize a first protocol and controller 106-2 canutilize a second protocol. In some examples, the first protocol can bedifferent than the second protocol.

In some examples, one of the plurality of controllers 106-1, 106-2,106-3 in a first zone of the plurality of zones 104-1, 104-2, 104-3 canalter or change a number of settings for the plurality of access points102-1, 102-2, 102-3 without altering settings of a second zone of theplurality of zones 104-1, 104-2, 104-3. For example, controller 106-2within zone 104-2 can alter settings of the access points 102-1, 102-2,102-3 that correspond to zone 104-2. In this example, the alteredsettings corresponding to the zone 104-2 may not affect settings of zone104-1 or zone 104-3. That is, the controller 106-2 can alter settings ofthe access points 102-1, 102-2, 102-3 for the connection between theplurality of access points 102-1, 102-2, 102-3 and the controller 106-2without altering settings of the access points 102-1, 102-2, 102-3 andthe controllers 106-1, 106-3.

In some examples, the plurality of controllers 106-1, 106-2, 106-3 caneach utilize an encryption and/or decryption method. In some examples,each of the plurality of controllers 106-1, 106-2, 106-3 can utilize adifferent encryption and/or decryption method. For example, controller106-1 can utilize a first type of encryption method for data packetsreceived from or sent to the plurality of access points 102-1, 102-2,102-3 and controller 106-2 can utilize a second type of encryptionmethod for data packets received from or sent to the plurality of accesspoints 102-1, 102-2, 102-3. In these examples, the plurality ofcontrollers 106-1, 106-2, 106-3 can utilize different encryption and/ordecryption methods such that data packets to be sent to controller 106-1are not capable of being decrypted by controller 106-2. These examplescan increase security between the plurality of controllers 106-1, 106-2,106-3.

In some examples, the plurality of zones 104-1, 104-2, 104-3 can includeservice controllers (SC) 110-1, 110-2. In some examples, each of theplurality of zones 104-1, 104-2, 104-3 can include a correspondingservice controller 110-1, 110-2. In some examples, the servicecontrollers 110-1, 110-2 can correspond to controllers 106-1, 106-2within the corresponding zones 104-1, 104-2. For example, zone 104-1 caninclude a controller 106-1 and a corresponding service controller 110-1.In some examples, service controllers 110-1, 110-2 can generate securityprotocols for the corresponding controllers 106-1, 106-2. In someexamples, the service controllers 110-1, 110-2 can be utilized to definesecurity protocols for a corresponding zone 104-1, 104-2. In someexamples, the service controllers 110-1, 110-2 can be utilized to altersecurity protocols or other security settings for the corresponding zone104-1, 104-2.

In some examples, the plurality of zones 104-1, 104-2, 104-3 can beorganized in a hierarchy with primary zones with higher priority oversecondary zones. For example, zone 104-1 can have priority over zone104-2. For example, the controller 106-1 can be a primary zone thatincludes administrative control and/or management over the plurality ofaccess points 102-1, 102-2, 102-3. In this example, administrativesettings for the plurality of access points 102-1, 102-2, 102-3 may bealtered by the controller 106-1 while the administrative settings maynot be altered by controllers 106-2, 106-3.

As used herein, administrative settings for the plurality of accesspoints 102-1, 102-2, 102-3 can include, but is not limited to debuglogs, common information logs, troubleshooting settings, managementsettings, quantity of zones settings, radio configuration, channelconfiguration, multi-connection profile, reboot capabilities for thecontrollers 106-1, 106-2, 106-3, reboot capabilities for the accesspoints 102-1, 102-2, 102-3, and/or other administrative settings thatmay not affect settings of the other zones 104-2, 104-3. For example,the controller 106-1 can alter a quantity of zones for the plurality ofaccess points 102-1, 102-2, 102-3. In some examples, the zone 104-2 canbe a secondary zone that does not have priority over zone 104-1. In thisexample, controller 106-2 of zone 104-2 can connect to the plurality ofaccess points 102-1, 102-2, 102-3 after the controller 106-1 of zone104-1 connects to the plurality of access points 102-1, 102-2, 102-3. Inthis example, the controller 106-2 of zone 104-2 can receive themulti-connection configuration from the controller 106-1. As usedherein, the multi-connection configuration can include theadministrative settings as described herein for the environment 100. Insome examples, the controller 106-2 can be restricted to providingtunnel mode for the plurality of access points 102-1, 102-2, 102-3, Inthis way the environment 100 may not experience counteractive settingsor setting changes that negatively affect the environment 100.

The environment 100 can be utilized to enable the plurality of accesspoints 102-1, 102-2, 102-3 to have multiple zones 104-1, 104-2, 104-3that are managed by corresponding controllers 106-1, 106-2, 106-3. Insome examples, the multiple zones 104-1, 104-2, 104-3 can be separatedby air gaps to prevent data packets from being decrypted by an incorrectcontroller. In some examples, the environment 100 can be utilized toenable a first controller for a first type of data and enable a secondcontroller for the same access points for a second type of data. In thisway, an organization can separate the management of secure data fromunsecure data. In another way, multiple organizations can utilize theenvironment 100 to limit a quantity of access points within an areawhile maintaining security and separation between the multipleorganizations.

FIG. 2 further illustrates an example method 220 for multi-connectionaccess point, consistent with the present disclosure. In some examples,the method 220 can be utilized to generate the multi-connection accesspoint environment 100 as referenced in FIG. 1. For example, the method220 can be a multi-connection configuration of a plurality of accesspoints and/or a plurality of controllers. The method 220 can be executedby an access point 202 and/or a number of zones 204-1, 204-2, 204-3 withcorresponding controllers as described herein.

At 222, the method 220 can include the access point 202 connecting to acontroller corresponding to zone 204-1. As described herein, the numberof zones 204-1, 204-2, 204-3 can be in a hierarchy. For example, zone204-1 can be considered a primary zone (PZ) when the zone 204-1 is a topzone within the hierarchy. For example, the zone 204-1 can be utilizedto manage administrative settings for the access point 202 as describedherein. In some examples, the controllers corresponding to zone 204-1can: be a first zone to connect with the access point 202, have fullcontrol of the access point 202, have radio control over the accesspoint 202, have channel configuration control over the access point 202,and/or control other features of the access point 202. In some examples,a controller corresponding to zone 204-1 can configure Internetprotocols (IPs) for controllers corresponding to zone 204-2 and/or zone204-3.

At 224-1, the method 220 can include notifying, by the controllercorresponding to the zone 204-1, the IPs for controllers correspondingto zone 204-2 and/or zone 204-3. The access point 202 can receive thenotification from the controller corresponding to zone 204-1. At 224-2,the method 220 can include the access point 202 performing an accesspoint self-check. At 224-3, the method 220 can include the access point202 determining an ESSID assignment table (EAT) allocation based on thenotification and/or self-check.

At 226-1, the method 220 can include the controllers corresponding tozone 204-1 configuring virtual access points for controllerscorresponding to zone 204-2 and/or zone 204-3. As used herein, a virtualaccess point is an emulation of an access point. In some examples, theaccess point 202 can include a plurality of virtual access points thateach can virtually act as individual physical access points. At 226-2,the method 220 can include the access point 202 starting the virtualaccess points for zone 204-1. In some examples, starting the virtualaccess point for zone 204-1 can include starting communication of datapackets between the access point 202 and the controllers correspondingto zone 204-1. In some examples, the access point 202 can start thevirtual access points for the zone 204-1 based on the configuration fromzone 204-1 at 226-1.

At 228, the method 220 can include the access point 202 sending a zoneflag (e.g., data zone (DZ) flag, etc.) to zone 204-2. In some examples,the access point 202 can simultaneously send a zone flag to zone 204-2and zone 204-3. In these examples, the access point 202 can startvirtual access points for a zone that responds to the zone flag first.For example, controllers corresponding to zone 204-2 can sendconfiguration data to the access point 202 in response to the zone flagsent at 228 before controllers corresponding to zone 204-3 can respond.

At 232, the method 220 can include the access point 202 starting virtualaccess points for controllers corresponding to zone 204-2. As describedherein, starting the virtual access points for the controllerscorresponding to zone 204-2 can include starting communication of datapackets between the access point 202 and controllers corresponding tozone 204-2. In some examples, the controllers corresponding to zone204-2 can be data zone (DZ) controllers that are lower in the zonehierarchy compared to zone 204-1. That is, the controllers correspondingto zone 204-2 can include limited capabilities. For example, thecontrollers corresponding to zone 204-2 may not be able to reboot theaccess point 202, provision the access point 202, and/or upgrade animage of the access point 202.

At 234, the method 220 can include the access point 202 sending a zoneflag (e.g., data zone (DZ) flag, etc.) to zone 204-3. In some examples,the controllers corresponding to zone 204-3 can respond at 236 withconfiguration data for virtual access points for the controllerscorresponding to zone 204-3. For example, controllers corresponding tozone 204-3 can send configuration data to the access point 202 inresponse to the zone flag sent at 234.

At 238, the method 220 can include the access point 202 starting virtualaccess points for controllers corresponding to zone 204-3. As describedherein, starting the virtual access points for the controllerscorresponding to zone 204-3 can include starting communication of datapackets between the access point 202 and controllers corresponding tozone 204-3. In some examples, the controllers corresponding to zone204-3 can be data zone (DZ) controllers that are lower in the zonehierarchy compared to zone 204-1. That is, the controllers correspondingto zone 204-3 can include limited capabilities. For example, thecontrollers corresponding to zone 204-3 may not be able to reboot theaccess point 202, provision the access point 202, and/or upgrade animage of the access point 202.

FIG. 3 illustrates an example architecture 340 for multi-connectionaccess point, consistent with the present disclosure. In some examples,the architecture 340 can represent a networking environment such asenvironment 100 as illustrated in FIG. 1. The architecture 340 canillustrate an access point 302 connected to a plurality of zones 304-1,304-2, 304-3 with corresponding controllers (e.g., controller 306-1,306-2, 306-3 and/or service controllers 310-1, 310-2, etc.).

The access point 302 can include a station 342. As used herein, astation 342 is a device that can utilize networking protocols (e.g.,IEEE 802.11, etc.). In some examples, the access point 302 can beconfigured to generate a plurality of virtual access points from thestation 342. As used herein, a virtual access point is an emulation ofthe access point 302. In some examples, the virtual access points foreach of the plurality of zones 304-1, 304-2, 304-3 can include: a numberof control plane security (CPSec) engines 344-1, 344-2, 344-3 forcontrollers 306-1, 306-2, 306-3, control plane security engines 346-1,346-2 for service controllers 310-1, 310-2, and/or basic service set(BSS) engines 348-1, 350, 348-2, 348-3. As used herein, a BSS includesthe access point 302 and associated station 342.

In some examples, the zone 304-1 can include a controller 306-1 coupledto CPSec engine 344-1, BSS engine 348-1, and/or BSS engine 350. In someexamples, the zone 304-1 can include a service controller 310-1 coupledto CPSec engine 346-1, BSS 348-1, and/or BSS engine 350. In someexamples, the zone 304-1 can be a primary zone as described herein.

In some examples, the zone 304-2 can include a controller 306-2 coupledto CPSec engine 344-2, and/or BSS engine 342-2. In some examples, thezone 304-2 can include a service controller 310-2 coupled to CPSecengine 346-2 and/or BSS engine 348-2. In some examples, the zone 304-2can be a data zone as described herein. In some examples, the zone 304-3can include a controller 306-3 coupled to CPSec engine 344-3 and/or BSSengine 348-3. In some examples, the zone 304-3 may not include a servicecontroller. In some examples, the zone 304-3 can be a data zone asdescribed herein.

FIG. 4 is a block diagram of an example system 450 for multi-connectionaccess point, consistent with the present disclosure. The system 450 mayinclude a computing device that is capable of communicating with aremote system. In the example of FIG. 4, the system 450 includes aprocessing resource 452 and a memory resource 454. The memory resource454 may store readable instructions to cause the processing resource 452to perform a number of operations. Although the following descriptionsrefer to a single processing resource and a single memory resource, thedescriptions may also apply to a system with multiple processingresources and multiple memory resources. In such examples, theinstructions may be distributed across multiple memory resources and theinstructions may be distributed across multiple processing resources.Put another way, the instructions may be stored across multiplemachine-readable storage mediums and executed across multiple processingresources, such as in a distributed computing environment.

Processing resource 452 may be a central processing unit (CPU),microprocessor, and/or other hardware device suitable for retrieval andexecution of instructions stored in memory resource 454. In theparticular example shown in FIG. 4, processing resource 452 may receive,determine, and send instructions 456, 458, 460, 462. As an alternativeor in addition to retrieving and executing instructions, processingresource 452 may include an electronic circuit comprising a number ofelectronic components for performing the operations of the instructionsin the memory resource 454. With respect to the executable instructionrepresentations or boxes described and shown herein, it should beunderstood that part or all of the executable instructions and/orelectronic circuits included within one box may be included in adifferent box shown in the figures or in a different box not shown.

Memory resource 454 may be any electronic, magnetic, optical, or otherphysical storage device that stores executable instructions. Thus,memory resource 454 may be, for example, Random Access Memory (RAM), anElectrically-Erasable Programmable Read-Only Memory (EEPROM), a storagedrive, an optical disc, and the like. The executable instructions may bestored on the memory resource 454. Memory resource 454 may be aportable, external or remote storage medium, for example, that allowsthe system to download the instructions from theportable/external/remote storage medium. In this situation, theexecutable instructions may be part of an “installation package”. Asdescribed herein, memory resource 454 may be encoded with executableinstructions for network authentication system extensions.

The system 450 may also include instructions 456 executable by aprocessing resource, such as processing resource 452, to establish afirst connection with a first controller corresponding to a first zoneof a network. Establishing a first connection with a first controllercan include connecting to a controller corresponding to a primary zoneas described herein (e.g., 222 in method 220 as referenced in FIG. 2,etc.), In some examples, establishing a connection to the firstcontroller can include sending a zone flag to the first controller asdescribed herein. In some examples, establishing a connection to thefirst controller can include sending the zone flag to initiate the firstcontroller to configure IPs for a plurality of additional zones withcorresponding controllers as described herein.

The system 450 may also include instructions 458 executable by aprocessing resource, such as processing resource 452, to receiveconfiguration data to establish a first virtual access pointcorresponding to the first controller. As described herein, the firstcontroller can send configuration data such as IP configuration data fora plurality of additional zones and/or controllers. In some examples,the first controller can send configuration information for establishinga connection between the access point and the first controller. As usedherein, ‘information’ is generally defined as data, address, control,management (e.g., statistics) or any combination thereof. Fortransmission, information may be transmitted as a message, namely acollection of bits in a predetermined format. One type of message,namely a wireless message, includes a header and payload data having apredetermined number of bits of information. The wireless message may beplaced in a format as one or more packets, frames or cells.

As described herein, establishing a connection between the access pointand the first controller can include establishing a virtual access pointto communicate data packets between the access point and the firstcontroller. As described herein, a virtual access point can include anemulation of the access point that can act as a separate and distinctaccess point.

The system 450 may also include instructions 460 executable by aprocessing resource, such as processing resource 452, to establish asecond connection with a second controller corresponding to a secondzone of the network. In some examples, establishing a second connectionto the second controller can include sending a zone flag to the secondcontroller. In some examples, the zone flag can include an EAT toidentify a hierarchy of the second controller. For example, the secondcontroller can be a controller within a data zone as described herein.

The system 450 may also include instructions 462 executable by aprocessing resource, such as processing resource 452, to receiveconfiguration data to establish a second virtual access pointcorresponding to the second controller. As described herein, theconfiguration data can be received to configure the second virtualaccess point corresponding to the second controller. Upon configuringthe second virtual access point, the instructions 462 can includefurther instructions to start the second virtual access point andestablish a connection for communicating data packets between the secondcontroller and the second virtual access point. In some examples, theconfiguration data to establish the first virtual access point includesa first ESSID and the configuration data to establish the second virtualaccess point includes a second ESSID.

In some examples, the system 450 can receive data packets and/or datatraffic from a plurality of other network devices and/or user devicesvia a network. As used herein, ‘network device’ generally includes adevice that is adapted to transmit and/or receive signaling and toprocess information within such signaling such as a station (e.g., anydata processing equipment such as a computer, cellular phone, personaldigital assistant, tablet devices, etc.), an access point, data transferdevices (such as network switches, routers, controllers, etc.) or thelike. In some examples, the traffic includes an ESSID that can becompared to an ESSID of the first controller and/or the secondcontroller. In these examples, received traffic including the firstESSID is transferred to the first controller and received trafficincluding the second ESSID is transferred to the second controller.

FIG. 5 is a block diagram of an example method 570 for multi-connectionaccess point, consistent with the present disclosure. In some examples,the method 570 can be performed by a computing device, such as acomputing device of system 450 as referenced in FIG. 4. The method 570can be utilized to establish a multi-connection access point environmentas described herein. For example, the method 570 can be utilized togenerate an networking environment, such as environment 100 asreferenced in FIG. 1.

At 572, the method 570 can include sending, by an access point, a firstconnection request to a first controller. As described herein, sending afirst connection request can include sending a first zone flag to thefirst controller. In some examples, the first controller can be in acorresponding zone that is a primary zone as described herein. In someexamples, the first connection request can include data relating to theaccess point. For example, the first connection request can includespecification data relating to the access point. In some examples, thefirst controller can utilize the data of the first connection request toconfigure the access point. For example, the first controller candetermine a quantity of virtual access points to be generated by theaccess point.

At 574, the method 570 can include receiving, by the access point,configuration data from the first controller to generate a first virtualaccess point on the access point. As described herein, the configurationdata can be received by the access point from the first controller thatcan be utilized by the access point to configure a plurality of virtualaccess points. In some examples, the access point can utilize theconfiguration data to determine additional controllers to sendadditional connection requests. For example, the configuration data canbe utilized to determine a second controller to send a second connectionrequest. In some examples, the configuration data can be utilized toconfigure settings of the access point when establishing a connectionwith the first access point and/or other access points.

At 576, the method 570 can include sending, by the access point, asecond connection request to a second controller, wherein the firstcontroller and the second controller are different controllers. Asdescribed herein, sending the second connection request to a secondcontroller can include sending a zone flag to a controller that isdifferent than the first controller. In some examples, the secondconnection request can be associated with a second virtual access point.In some examples, the second connection request can include an EAT thatis defined by the configuration data received by the first controller.

At 578, the method 570 can include receiving, by the access point,configuration data from the second controller to generate a secondvirtual access point on the access point. The configuration data fromthe second controller can include data to configure the communicationbetween the second controller and the second virtual access point. Asdescribed herein, the second controller may not have administrativecontrol over the access point. That is, the second controller is capableof managing the access point for communication between the secondcontroller and the second virtual access point, but not capable ofmanaging administrative settings.

In some examples, the method 570 can include receiving configurationdata from the first controller includes receiving configurationinstructions to send a plurality of additional connection requests toadditional controllers. As described herein, the configuration data fromthe first controller can identify a plurality of additional controllersfor the access point to send a connection request. In some examples, theconfiguration data from the first controller can include administrativesettings for the access point.

In some examples, the method 570 can include receiving, by the accesspoint, communication from a plurality of client devices communicativelycoupled to the access point. As described herein, the access point canbe a network device within a network. In some examples, the access pointcan receive data packets from a plurality of network devices. In theseexamples, the access point can determine an ESSID for the data packetsand send the data packets to a corresponding controller based on theESSID. As described herein, the first controller can utilize a firstESSID and the second controller can utilize a second ESSID that isdifferent than the first ESSID.

In some examples, the method 570 can include transferring, by the accesspoint, the communication to either the first controller or the secondcontroller based on the configuration data received from the firstcontroller. As described herein, the access point can transfer thecommunication and/or data packets based on the ESSID within thecommunication or data packet.

In some examples, the method 570 can include receiving, by the accesspoint, setting changes from the first controller and setting changesfrom the second controller, wherein the setting changes from the firstcontroller override the setting changes from the second controller. Asdescribed herein, the first controller can be within a primary zone andthe second controller can be within a data zone. In some examples, thefirst controller within the primary zone can be relatively higher in azone hierarchy compared to the second controller within the data zone.Thus, the first controller is capable of altering administrativesettings while the second controller is not capable of alteringadministrative settings.

In the foregoing detailed description of the present disclosure,reference is made to the accompanying drawings that form a part hereof,and in which is shown by way of illustration how examples of thedisclosure may be practiced. These examples are described in sufficientdetail to enable those of ordinary skill in the art to practice theexamples of this disclosure, and it is to be understood that otherexamples may be utilized and that process, electrical, and/or structuralchanges may be made without departing from the scope of the presentdisclosure.

The figures herein follow a numbering convention in which the firstdigit corresponds to the drawing figure number and the remaining digitsidentify an element or component in the drawing. Elements shown in thevarious figures herein can be added, exchanged, and/or eliminated so asto provide a number of additional examples of the present disclosure. Inaddition, the proportion and the relative scale of the elements providedin the figures are intended to illustrate the examples of the presentdisclosure, and should not be taken in a limiting sense. As used herein,the designator “N”, particularly with respect to reference numerals inthe drawings, indicates that a number of the particular feature sodesignated can be included with examples of the present disclosure. Thedesignators can represent the same or different numbers of theparticular features. Further, as used herein, “a number of” an elementand/or feature can refer to one or more of such elements and/orfeatures.

What is claimed:
 1. An access point, comprising instructions to:establish a first connection to a first controller, wherein the accesspoint receives configuration data from the first controller to generatea first virtual access point with the first controller; and establish asecond connection to a second controller, wherein the access pointreceives configuration data from the second controller to generate asecond virtual access point with the second controller.
 2. The accesspoint of claim 1, wherein the first controller and the second controllerare separated by a network air gap.
 3. The access point of claim 1,wherein the first controller utilizes a first protocol and the secondcontroller utilizes a second protocol.
 4. The access point of claim 1,wherein the access point provides services to a first zone and a secondzone.
 5. The access point of claim 4, wherein the first controllermanages services for the first zone and the second controller managesservices for the second zone.
 6. The access point of claim 1, whereinthe first controller manages settings of the access point.
 7. The accesspoint of claim 1, wherein the first controller includes a first securityclassification and a second controller includes a second securityclassification.
 8. A non-transitory memory resource includinginstructions executable by a processing resource to: establish a firstconnection with a first controller corresponding to a first zone of anetwork; receive configuration data to establish a first virtual accesspoint corresponding to the first controller; establish a secondconnection with a second controller corresponding to a second zone ofthe network; and receive configuration data to establish a secondvirtual access point corresponding to the second controller.
 9. Thememory resource of claim 8, wherein the configuration data to establishthe first virtual access point includes a first ESSID and theconfiguration data to establish the second virtual access point includesa second ESSID.
 10. The memory resource of claim 8, wherein receivedtraffic including the first ESSID is transferred to the first controllerand received traffic including the second ESSID is transferred to thesecond controller.
 11. A method, comprising: sending, by an accesspoint, a first connection request to a first controller; receiving, bythe access point, configuration data from the first controller togenerate a first virtual access point on the access point; sending, bythe access point, a second connection request to a second controller,wherein the first controller and the second controller are differentcontrollers; and receiving, by the access point, configuration data fromthe second controller to generate a second virtual access point on theaccess point.
 12. The method of claim 11, wherein receivingconfiguration data from the first controller includes receivingconfiguration instructions to send a plurality of additional connectionrequests to additional controllers.
 13. The method of claim 11,comprising receiving, by the access point, communication from aplurality of client devices communicatively coupled to the access point.14. The method of claim 13, comprising, transferring, by the accesspoint, the communication to either the first controller or the secondcontroller based on the configuration data received from the firstcontroller.
 15. The method of claim 11, comprising receiving, by theaccess point, setting changes from the first controller and settingchanges from the second controller, wherein the setting changes from thefirst controller override the setting changes from the secondcontroller.